System for distributing merchandise to passengers of a taxi service

ABSTRACT

In one embodiment a transportation request is received from a passenger having an account with a taxi service. A driver associated with the taxi service is directed to pick up the passenger and transport the passenger to a location specified by the passenger. It is determined that the passenger should be offered an item of merchandise to use temporarily. In response to the passenger accepting the item of merchandise, an update is sent to a data store, the update indicating that the passenger is in possession of the item of merchandise.

TECHNICAL FIELD

This disclosure relates in general to the field of mobile applicationsand, more particularly, to a system for distributing merchandise topassengers of a taxi service.

BACKGROUND

A taxi service may utilize a plurality of drivers that fulfill passengerrequests for transportation. A taxi service may provide one or moremobile applications that facilitate the efficient pairing of passengersand drivers. The taxi service may receive a passenger request and selecta driver to fulfill the request based on information associated with thepassenger request and information associated with the driver.

BRIEF DESCRIPTION OF THE DRAWINGS

To provide a more complete understanding of the present disclosure andfeatures and advantages thereof, reference is made to the followingdescription, taken in conjunction with the accompanying figures, whereinlike reference numerals represent like parts, in which:

FIG. 1 illustrates a block diagram of a system for distributingmerchandise to passengers of a taxi service in accordance with certainembodiments.

FIG. 2 illustrates a block diagram of a passenger mobile device and adriver mobile device of the system of FIG. 1 in accordance with certainembodiments.

FIG. 3 illustrates a block diagram of a backend system of the system ofFIG. 1 in accordance with certain embodiments.

FIG. 4 illustrates passenger inventory data of FIG. 3 in accordance withcertain embodiments.

FIG. 5 illustrates driver inventory data of FIG. 3 in accordance withcertain embodiments.

FIG. 6 illustrates a method for distributing merchandise to a passengerof a taxi service in accordance with certain embodiments.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

In one embodiment a transportation request is received from a passengerhaving an account with a taxi service. A driver associated with the taxiservice is directed to pick up the passenger and transport the passengerto a location specified by the passenger. It is determined that thepassenger should be offered an item of merchandise to use temporarily.In response to the passenger accepting the item of merchandise, anupdate is sent to a data store, the update indicating that the passengeris in possession of the item of merchandise.

EXAMPLE EMBODIMENTS

FIG. 1 illustrates a block diagram of a system for distributingmerchandise to passengers of a taxi service in accordance with certainembodiments. Although various embodiments may include any number ofdrivers, passengers, and associated devices, system 100 depicts twopassengers having associated passenger mobile devices 104 and twodrivers having associated driver mobile devices 108. The mobile devicesare coupled through various networks 120 to an application server 112and a backend system 116.

Various embodiments of the present disclosure may enhance the experienceof passengers associated with a taxi service by allowing them to borrowmerchandise from the taxi service temporarily. For example, a passengermay check out an umbrella or phone charger from a driver of the taxiservice following a ride provided by the driver, use the items for aperiod of time, and return the items to another driver of the taxiservice or to a designated location. In particular embodiments, adetermination of whether to offer a passenger merchandise may be basedon various factors, such as the amount of remaining merchandise in avehicle, the loyalty of the passenger, detected conditions (such as theweather or the battery state of a mobile device of the passenger), orother suitable factors.

Mobile devices 104 and 108 may include any electronic computing deviceoperable to receive, transmit, process, and store any appropriate data.For example, mobile devices 104 and 108 may include laptop computers,tablet computers, smartphones, personal digital assistants, and otherdevices capable of connecting (e.g., wirelessly) to one or more networks120. Mobile devices 104 and 108 may include a set of programs such asoperating systems (e.g., Microsoft Windows, Linux, Android, Mac OSX,Apple iOS, UNIX, or similar operating system), applications, plug-ins,applets, virtual machines, machine images, drivers, executable files,and other software-based programs capable of being run, executed, orotherwise used by the respective devices. Each mobile device can includeat least one graphical display and user interface allowing a user toview and interact with applications and other programs of the mobiledevice. In a particular embodiment, a driver mobile device may be ahardened device that is configured to only run a taxi driver applicationusing a specialized operating system (e.g., a modified version ofAndroid). In one embodiment, a taxi service may issue or otherwisefacilitate the provision of hardened devices to its drivers, butrestrict the functionality of the devices to the taxi driver application(i.e., the devices may be locked down so as not to allow theinstallation of additional applications).

In various embodiments, a driver mobile device 108 may be integratedwithin and/or communicate with a self-driven vehicle (e.g., a vehiclethat has the capability of driving without physical steering guidancefrom a human being) and may influence the movement of the vehicle byproviding route information (e.g., passenger pick-up and destinationlocations or driver destination locations) to the self-driven vehicle.Accordingly, as used herein “driver” may refer to a human being that mayphysically drive or otherwise control movement of a vehicle or thevehicle itself (e.g., in the case of a self-driven vehicle) or componentthereof (e.g., mobile device application 108 or logic therein).

In particular embodiments, a taxi passenger application runs onpassenger mobile devices 104. The application may allow a user to entervarious account information (e.g., in connection with a registrationwith the taxi service) to be utilized by a taxi service. For example,the account information may include a user name and password (or otherlogin credentials), contact information of the user (e.g., phone number,home address), payment information (e.g., credit card numbers or bankaccount numbers and associated information), or car preferenceinformation (e.g., what models or color of car the user prefers).

The application may allow a user to request a ride from the taxiservice. In various embodiments, the application may establish a pick-uplocation automatically or based on user input (e.g., locations mayinclude the current location of the mobile device 104 as determined by aglobal positioning system (GPS) of the mobile device or a differentuser-specified location). In certain embodiments, the user may specify adestination location as well. The locations may be specified in anysuitable format, such as GPS coordinates, street address, establishmentname (e.g., LaGuardia Airport, Central Park, etc.), or other suitableformat. At any time (e.g., before the ride, during the ride, or afterthe ride is complete) the user may specify a method of payment to beused for the ride. The user may also specify whether the request is forimmediate pick-up or for a specified time in the future. In variousembodiments, the user may specify pick-up by a vehicle that hasparticular merchandise available for use by the user, such as aspecified type of battery or battery charger, bottle of water or otherfood or beverage, umbrella, or other suitable merchandise. The user mayalso specify criteria for the driver, such as a minimum performancerating, such that drivers having performance ratings below the minimumperformance rating will not be considered during selection of thedriver.

The user may use the application to order a ride based on the specifiedinformation. The request for the ride is generated based on theinformation and transmitted to backend system 116. Backend system 116will facilitate the selection of a driver. In some embodiments, backendsystem 116 may select a driver based on any suitable factors, such asthe information contained in the request from the passenger, theproximity of the driver to the passenger, or other suitable factors. Inother embodiments, backend system 116 may select a plurality of driversthat could fulfill the ride request, send information associated withthe drivers to the passenger, and allow the passenger to select thedriver to be used via the application on the passenger mobile device104. Any suitable information about the potential driver(s) may be sentto the mobile device 104 either before or after the selection of thedriver by the passenger, such as a location of a driver, an estimatedpick-up time, a type of car used by a driver, the merchandise availablein the car, a driver rating or comments made by other passengers aboutthe driver, or other suitable information.

Once a driver has been selected and has accepted the request to providea ride, the application may notify the user of the selected driver andprovide real-time updates of the driver's location (e.g., with respectto the passenger's location) and estimated pick-up time. The applicationmay also provide contact information for the driver and/or the abilityto contact the driver through the application (e.g., via a phone call ortext). Once the ride has begun, the application may display any suitableinformation, such as the current location of the mobile device 104 andthe route to be taken. Upon completion of the ride, the application mayprovide the passenger the ability to rate the driver or provide commentsabout the driver.

In particular embodiments, a taxi driver application runs on drivermobile devices 108. The application may allow a driver to enter variousaccount information to be utilized by a taxi service. For example, theaccount information may include a user name and password (or other logincredentials), contact information of the driver (e.g., phone number,home address), information used to receive payments from the taxiservice (e.g., bank account information), vehicle information (e.g.,what model or color of car the driver utilizes), merchandise offered bythe driver, or other suitable information.

In various embodiments, the application may allow a driver to specifyhis availability to transport passengers for the taxi service. Theapplication may periodically transmit the current location of the mobiledevice 108 as determined by a GPS of the mobile device 108 to thebackend system 116. When a driver is selected to provide a ride, backendsystem 116 may send a notification to the taxi driver application. Insome embodiments, the driver may have a limited amount of time to selectwhether the driver accepts the ride. In other embodiments, theapplication may be configured by the driver to automatically accept theride or to automatically accept the ride if certain criteria are met(e.g., fare minimum, direction of travel, minimum passenger rating,etc.).

Once a pairing of the driver and the passenger is confirmed, theapplication may navigate the driver to the passenger. The applicationmay also provide contact information for the passenger and/or theability to contact the passenger through the application (e.g., via aphone call or text). The application may also navigate the driver to thepassenger's destination once the ride begins. Upon completion of theride, the application may provide the driver the ability to rate thepassenger or provide comments about the passenger.

System 100 may include one or more application servers 112 coupled tothe mobile devices through one or more networks 120. The taxi passengerapplication and taxi driver application may be supported with,downloaded from, served by, or otherwise provided through an applicationserver 112 or other suitable means. In some instances, the applicationscan be downloaded from an application storefront onto a particularmobile device using storefronts such as Google Android Market, Apple AppStore, Palm Software Store and App Catalog, RIM App World, etc., as wellas other sources. In various embodiments, the taxi passenger applicationand taxi driver application may be installed on their respective devicesin any suitable manner and at any suitable time. As one example, a taxipassenger application may be installed on a mobile device as part of asuite of applications that are pre-installed prior to provision of themobile device to a consumer. As another example, a taxi driverapplication may be installed on a mobile device by a taxi service (or anentity that provisions mobile devices for the taxi service) prior to theissuance of the device to a driver that is employed by or otherwiseassociated with the taxi service.

As described above, applications utilized by mobile devices 104 and 108can make use of a backend system 116. Backend system 116 may compriseany suitable servers or other computing devices that facilitate theprovision of a taxi service as described herein. For example, backendsystem 116 may receive a request from a passenger and facilitate theassignment of a driver to fulfill the request. Backend system 116 isdescribed in more detail in connection with FIG. 3.

In general, “servers,” and other “computing devices” may includeelectronic computing devices operable to receive, transmit, process,store, or manage data and information associated with system 100. Asused in this document, the term “computing device,” is intended toencompass any suitable processing device. For example, portions ofsystem 100 may be implemented using computers other than servers,including server pools or other suitable processing devices. Further,any, all, or some of the computing devices may be adapted to execute anyoperating system, including Linux, UNIX, Windows Server, etc., as wellas virtual machines adapted to virtualize execution of a particularoperating system, including customized and proprietary operatingsystems.

Further, servers and other computing devices of system 100 can eachinclude one or more processors, computer-readable memory, and one ormore interfaces, among other features and hardware. Servers can includeany suitable software component or module, or computing device(s)capable of hosting and/or serving a software application or services(e.g., services of application server 112 or backend system 116),including distributed, enterprise, or cloud-based software applications,data, and services. For instance, servers can be configured to host,serve, or otherwise manage data sets, or applications interfacing,coordinating with, or dependent on or used by other services, includingtaxi service applications and software tools. In some instances, aserver, system, subsystem, or computing device can be implemented assome combination of devices that can be hosted on a common computingsystem, server, server pool, or cloud computing environment and sharecomputing resources, including shared memory, processors, andinterfaces.

In various embodiments, backend system 116 or any components thereof maybe deployed using a cloud service such as Amazon Web Services, MicrosoftAzure, or Google Cloud Platform. For example, the functionality of thebackend system 116 may be provided by virtual machine servers that aredeployed for the purpose of providing such functionality or may beprovided by a service that runs on an existing platform.

System 100 also includes various networks 120 used to communicate databetween the mobile devices 104 and 108, the backend system 116, and theapplication server 112. The networks 120 described herein may be anysuitable network or combination of one or more networks operating usingone or more suitable networking protocols. A network may represent aseries of points, nodes, or network elements and interconnectedcommunication paths for receiving and transmitting packets ofinformation. For example, a network may include one or more routers,switches, firewalls, security appliances, antivirus servers, or otheruseful network elements. A network may provide a communicative interfacebetween sources and/or hosts, and may comprise any public or privatenetwork, such as a local area network (LAN), wireless local area network(WLAN), metropolitan area network (MAN), Intranet, Extranet, Internet,wide area network (WAN), virtual private network (VPN), cellular network(implementing GSM, CDMA, 3G, 4G, LTE, etc.), or any other appropriatearchitecture or system that facilitates communications in a networkenvironment depending on the network topology. A network can compriseany number of hardware or software elements coupled to (and incommunication with) each other through a communications medium. In someembodiments, a network may simply comprise a transmission medium such asa cable (e.g., an Ethernet cable), air, or other transmission medium.

FIG. 2 illustrates a block diagram of a passenger mobile device 104 anda driver mobile device 108 of the system of FIG. 1 in accordance withcertain embodiments. In the embodiment shown, the devices may becommunicatively coupled through network 120 f which may include anysuitable intermediary nodes, such as a backend system 116.

In the embodiment depicted, mobile devices 104 and 108 each include acomputer system to facilitate performance of their respectiveoperations. In particular embodiments, a computer system may include aprocessor, storage, and one or more communication interfaces, amongother components. As an example, mobile devices 104 and 108 each includeone or more processors 202 and 204, memory elements 206 and 208, andcommunication interfaces 214 and 216, among other hardware and software.These components may work together in order to provide functionalitydescribed herein.

Processors 202 and 204 may be a microprocessor, controller, or any othersuitable computing device, resource, or combination of hardware, storedsoftware and/or encoded logic operable to provide, either alone or inconjunction with other components of mobile devices 104 and 108, thefunctionality of these mobile devices. In particular embodiments, mobiledevices 104 and 108 may utilize multiple processors to perform thefunctions described herein. In various embodiments, a processor mayinclude multiple discrete processors communicatively coupled together.

A processor can execute any type of instructions to achieve theoperations detailed in this Specification. In one example, the processorcould transform an element or an article (e.g., data) from one state orthing to another state or thing. In another example, the activitiesoutlined herein may be implemented with fixed logic or programmablelogic (e.g., software/computer instructions executed by the processor)and the elements identified herein could be some type of a programmableprocessor, programmable digital logic (e.g., a field programmable gatearray (FPGA), an erasable programmable read only memory (EPROM), anelectrically erasable programmable ROM (EEPROM)) or an ASIC thatincludes digital logic, software, code, electronic instructions, or anysuitable combination thereof.

Memory 206 and 208 may comprise any form of non-volatile or volatilememory including, without limitation, random access memory (RAM),read-only memory (ROM), magnetic media (e.g., one or more disk or tapedrives), optical media, solid state memory (e.g., flash memory),removable media, or any other suitable local or remote memory componentor components. Memory 206 and 208 may store any suitable data orinformation utilized by mobile devices 104 and 108, including softwareembedded in a computer readable medium, and/or encoded logicincorporated in hardware or otherwise stored (e.g., firmware). Memory206 and 208 may also store the results and/or intermediate results ofthe various calculations and determinations performed by processors 202and 204.

Communication interfaces 214 and 216 may be used for the communicationof signaling and/or data between mobile devices 104 and 108 and one ormore networks (e.g., 120 f) and/or network nodes (e.g., backend system116 and application server 112) coupled to a network or othercommunication channel. For example, communication interfaces 214 and 216may be used to send and receive network traffic such as data packets.Each communication interface 214 and 216 may send and receive dataand/or signals according to a distinct standard such as an LTE, IEEE802.11, IEEE 802.3, or other suitable standard. Communication interfaces214 and 216 may include antennae and other hardware for transmitting andreceiving radio signals to and from other devices in connection with awireless communication session over one or more networks 120.

GPS units 210 and 212 may include any suitable hardware and/or softwarefor detecting a location of their respective mobile devices 104 and 108.For example, a GPS unit may comprise a system that receives informationfrom GPS satellites, wireless or cellular base stations, and/or othersuitable source and calculates a location based on this information (orreceives a calculated position from a remote source). In one embodiment,the GPS unit is embodied in a GPS chip.

Application logic 218 may include logic providing, at least in part, thefunctionality of the taxi passenger application described herein.Similarly, application logic 220 may include logic providing, at leastin part, the functionality of the taxi driver application describedherein. In a particular embodiment, the logic of devices 104 and 108 mayinclude software that is executed by processor 202 and 204. However,“logic” as used herein, may include but not be limited to hardware,firmware, software and/or combinations of each to perform a function(s)or an action(s), and/or to cause a function or action from anotherlogic, method, and/or system. In various embodiments, logic may includea software controlled microprocessor, discrete logic (e.g., anapplication specific integrated circuit (ASIC)), a programmed logicdevice (e.g., a field programmable gate array (FPGA)), a memory devicecontaining instructions, combinations of logic devices, or the like.Logic may include one or more gates, combinations of gates, or othercircuit components. Logic may also be fully embodied as software.

In various embodiments of the present disclosure, in addition to anycombination of the features described above with respect to the taxipassenger application, application logic 218 may provide additionalfeatures for the taxi passenger application to enhance a passenger'sexperience. In a particular embodiment, a passenger may indicate one ormore items of merchandise within the taxi passenger application inassociation with a request for a ride, such that the taxi service mayselect a vehicle carrying the indicated item(s) of merchandise tofulfill the passenger's request.

In another embodiment, taxi passenger application may display anindication of one or more items of merchandise available (or indicationsthereof) in a particular vehicle (e.g., a prospective vehicle fortransporting the passenger or the vehicle that is fulfilling thepassenger's request) to the passenger. In particular embodiments, thetaxi passenger application may also display terms associated with themerchandise (e.g., a length of a borrowing period, a price associatedwith the merchandise, etc.). In some embodiments, the passenger mayselect merchandise and/or accept offers of merchandise via the taxipassenger application, and in response the merchandise may be dispensedto the passenger during or after the ride (in other embodiments, thedriver passenger application could be used to indicate to the taxiservice that particular merchandise has been dispensed to a user).

After the passenger has taken possession of the merchandise, the taxipassenger application may provide information associated with themerchandise. For example, the taxi passenger application may display atime and/or date when the passenger accepted the merchandise, a timeand/or date when the merchandise is due, an amount per day, week, orother interval that will be charged when the merchandise is not returnedby the due date, a maximum amount that will be charged for the item,indications of one or more locations or vehicles to which themerchandise may be returned, or other suitable information. In someembodiments, the taxi passenger application may provide reminders toreturn the merchandise at one or more suitable intervals (such as a daybefore the merchandise is due or every day after the merchandise is due)when the app is opened or via push notifications to the device on whichthe application is installed.

In various embodiments of the present disclosure, in addition to anycombination of the features described above with respect to the taxidriver application, application logic 220 may provide additionalfeatures for the taxi driver application to enhance the service a drivermay provide to a passenger. In an embodiment, the driver applicationlogic may receive an indication that an item of merchandise has beengiven to a passenger. As an example, a driver may enter informationthrough an interface implemented by the driver application logicindicating that an item of merchandise has been checked out to apassenger. As another example, the driver application logic may sensethat an item of merchandise has been received by a passenger (e.g., thelogic may sense that a locater device, such as a radio frequencyidentification tag, collocated with the item of merchandise has left thevehicle at the end of a ride).

The taxi driver application logic may allow the driver to requestinventory. For example, the application logic 220 may send a request forthe inventory to backend system 116. In various embodiments, the drivermay initiate the sending of the request through application logic 220 orthe application logic 220 may send the request when it detects thatinventory of a particular type of merchandise in the vehicle of thedriver is depleted or running low (e.g., below a predeterminedthreshold). The backend system 116 may facilitate the restocking of therequested inventory. As various examples, backend system 116 may notifythe driver of a nearby location at which the driver may pick upadditional inventory, may notify the driver of the location of anotherdriver associated with a vehicle carrying merchandise that may betransferred to the vehicle running low on inventory, or may initiate theshipping of additional merchandise items to a location (e.g., home)associated with the driver.

The taxi driver application logic may also allow the driver to check inmerchandise items from a passenger. For example, when a passengerrequests a ride from a driver, the passenger may return to the driver anitem of merchandise that was borrowed during a previous trip fulfilledby a driver of the taxi service. When an item is checked in oradditional items are picked up, the taxi driver application may allowthe driver to update a record of the amount of inventory.

The application logic 220 may communicate any suitable information tothe backend system 116. For example, application logic 220 maycommunicate driver requests for inventory, check-outs of inventory,check-ins of inventory, transfers of inventory to other drivers,reception of inventory, or other suitable information.

FIG. 3 illustrates a block diagram of a backend system 116 of the systemof FIG. 1 in accordance with certain embodiments. Although FIG. 3depicts a particular implementation of the backend system 116, thebackend system may include any suitable devices to facilitate theoperation of the taxi service described herein. In the embodimentdepicted, backend system includes backend server 302, data store 304,and third party services 306 coupled together by network 120 g. Invarious embodiments, backend server 302, data store 304, and/or thirdparty services 306 may each comprise one or more physical devices (e.g.,servers or other computing devices) providing the functionalitydescribed herein. In some embodiments, one or more of backend server302, data store 304, and third party services 306 (or portions thereof)are deployed using a cloud service and may comprise one or more virtualmachines or containers.

In the embodiment depicted, backend server 302 include a computer systemto facilitate performance of its operations. As an example, backendserver 302 includes one or more processors 308, memory elements 310, andcommunication interfaces 312, among other hardware and software. Thesecomponents may work together in order to provide backend serverfunctionality described herein. Processor 308 may have any suitablecharacteristics of the processors 202 and 204 described above. Inparticular embodiments, backend server 302 may utilize multipleprocessors to perform the functions described herein. In variousembodiments, a processor may include multiple discrete processorscommunicatively coupled together.

Similarly, memory 310 may have any suitable characteristics of memories206 and 208 described above. Memory 310 may store any suitable data orinformation utilized by backend server 302, including software embeddedin a computer readable medium, and/or encoded logic incorporated inhardware or otherwise stored (e.g., firmware). Memory 310 may also storethe results and/or intermediate results of the various calculations anddeterminations performed by processor 308.

Communication interface 312 may also have any suitable characteristicsof communication interfaces 214 and 216 described above. Communicationinterfaces 312 may be used for the communication of signaling and/ordata between backend server 302 and one or more networks (e.g., networks120) and/or network nodes (e.g., mobile devices 104 and 108, data store304, third party services 306, and application server 112) coupled to anetwork or other communication channel.

Business logic 314 may have any suitable characteristics of applicationlogic 218 and 220 described above. Business logic 314 may include logicproviding, at least in part, the functionality of the backend serverdescribed herein. In a particular embodiment, business logic 314 mayinclude software that is executed by processor 308. However, in otherembodiments, business logic 314 may take other forms such as thosedescribed above with respect to application logic 218 and 220.

Backend server 302 may communicate with data store 304 to initiatestorage and retrieval of data related to the taxi service. Data store304, may store any suitable data associated with the taxi service in anysuitable format(s). For example, data store 304 may include one or moredatabase management systems (DBMS), such as SQL Server, Oracle, Sybase,IBM DB2, or NoSQL data bases (e.g., Redis and MongoDB).

In the embodiment depicted, data store 304 includes passenger accountdata 316, driver account data 318, passenger request data 320, driveravailability data 322, navigational data 324, historical request data326, passenger inventory data 332, driver inventory data 334, andgeneral inventory data 336. The various data may be updated at anysuitable intervals.

Passenger account data 316 may include any suitable informationassociated with passenger accounts, such as contact information (e.g.,real names and addresses), user names and passwords (or otherauthentication information), payment information (e.g., credit card orbank account numbers and associated information), passenger preferences(e.g., preferred type or color of car), ratings the passenger has givendrivers, ratings the passenger has received from drivers, or otherinformation associated with passenger profiles.

Driver account data 318 may include any suitable information associatedwith driver accounts, such as contact information (e.g., real names andaddresses), user names and passwords (or other authenticationinformation), payment collection information (e.g., bank accountinformation), vehicle information (e.g., models and colors of cars thedrivers utilize, maximum capacity of the cars of the drivers),merchandise offered by the drivers, whether the drivers are available totransport passengers, whether the drivers have opted for automaticacceptance of passenger requests (whereby the backend server 302 mayassign a passenger request to the driver without waiting for the driverto indicate acceptance of a request), or other suitable information.

Passenger request data 320 may comprise pending requests (i.e., requeststhat have not yet been fulfilled) received from passengers. Each requestmay include any suitable information, such as any combination of one ormore of an identification of the passenger making the request, the timethe request was made, the current location of the passenger, the desiredpick-up location, the desired pick-up time, the estimated time remaininguntil a driver can pick up the passenger, the actual pick-up time, thedesired destination location of the passenger (which the passenger mayor may not provide at the time the request is made), the type of vehiclerequested, estimated fare for the trip, current accumulated fare for thetrip, estimated time and mileage remaining in the trip, otherinformation specified by the user (e.g., requested merchandise,requested minimum rating of driver), whether a driver has been assignedto a request, and which driver has been assigned to a request.

Driver availability data 322 may comprise information associated withdrivers that are available to transport passengers. In some embodiments,driver availability data 322 may also comprise information associatedwith drivers that are not available to transport passengers (e.g.,because they are off-duty or currently transporting a passenger). Anentry in the driver availability data 322 may include an identificationof a driver and any suitable associated information, such as one or moreof a current location of the driver, whether the driver is available totransport passengers, whether the driver is currently transporting apassenger, a destination location of a current trip of the driver, anestimate of how long it will be before the driver finishes his currenttrip, whether the driver has opted for automatic acceptance of passengerrequests, or other suitable information.

Navigational data 324 may comprise information supporting navigationfunctions provided by the taxi passenger applications and driverpassenger applications. For example, navigational data 324 may comprisemap data that may be sent to passenger mobile devices 104 and drivermobile devices 108 to allow the devices to display maps and associatedindicators (e.g., location of passenger(s), location of driver(s),desired routes, etc.) In some embodiments, the navigational data mayalso comprise information indicative of the amount of time required totravel between various locations. In some embodiments, navigational data324 may comprise historic and/or real time data about the flow oftraffic in particular areas enabling backend server 302 to calculate anestimated time required to travel from one location to another.

Historical request data 326 may comprise information about completedrequests. In some embodiments, historical request data 326 may alsoinclude information about canceled requests. The information for eachrequest may include any combination of the information listed above withrespect to requests stored in the passenger request data 320 as well asany combination of additional data such as the time at which thedestination location was reached, the total time of the trip, the totalfare, a rating given by the passenger to the driver or by the driver tothe passenger for the trip, or other suitable information associatedwith the trip.

Passenger inventory data 332 may include information associated withpassengers of the taxi service and inventory items associated with thosepassengers. Passenger inventory data 332 may include an entry for eachpassenger of any suitable number of passengers. Any suitable informationmay be included in an entry for a passenger, such as merchandisecurrently borrowed by the passenger, when the merchandise was borrowed,which driver the merchandise was borrowed from, where the merchandisewas borrowed (e.g., a physical location), when the merchandise is due,late fees associated with the merchandise (e.g., a daily or weekly latefee and/or a maximum late fee). The merchandise in possession of thepassenger may be identified in any suitable manner. For example, eachitem of merchandise could be tagged with a serial number or otheridentifier and this identifier may be stored in the entry of thepassenger that has possession of the item. As another example, the entryfor a passenger may merely identify a type of item (e.g., umbrella) inpossession by the passenger (as opposed to an identifier for thespecific item).

An entry for a passenger may also include historical records for pastmerchandise transactions by the passenger including any of theinformation listed above and additional information such as when theitem was returned, where the item was returned to, which driver thepassenger returned the item to, late fees incurred, or other suitableinformation. In various embodiments, an entry for a passenger may alsoinclude one or more indications of the suitability of the passenger toborrow merchandise. For example, the indications may include metrics onhow often the passenger requests rides from the taxi service, an averagecost for the passenger's rides with the taxi service, whether apassenger is a premium member of the taxi service (e.g., in oneembodiment, a premium membership may be offered by the taxi servicewhere one of the benefits of the premium membership is access tomerchandise), a relative ranking with respect to other passengers of howdesirable a customer the passenger is (which could be based oninformation stored in passenger inventory data 332 or any otherinformation in data store 304) or other suitable information.

Driver inventory data 334 may include information associated withdrivers of the taxi service and inventory items associated with thosedrivers. In particular embodiments, driver inventory data 334 mayinclude an entry for each driver. In some embodiments, an entry mayinclude indications of quantities of different types of merchandise inpossession of the driver. An entry could also include identificationinformation for each item of merchandise held by the driver. Forexample, each item of merchandise could be tagged with a serial numberor other identifier and this identifier may be stored in the entry ofthe driver that has possession of the item. Driver inventory data 334might also include status information describing a condition of one ormore of the items of merchandise. For example, for a battery, the statusinformation may describe a charge state of the battery. For damageditems, the status information might include a description of the damageso that the taxi service may track damage incurred by each passenger.

General inventory data 336 may include any suitable informationfacilitating the provision of merchandise inventory to driversassociated with the taxi service. For example, general inventory data336 may include information identifying any number of locations that maydispense inventory to drivers as well as quantities of merchandiseavailable at such locations.

In various embodiments, backend server 302 may access third partyservices 306 through business logic 328 to access data 330. Third partyservices 306 may represent any suitable number of devices operated byany suitable number of third parties that are distinct from an entitythat operates the backend system 116 and/or data store 304. For example,in some embodiments the navigational data may be obtained from a thirdparty service 306 rather than data store 304, or additional third partynavigational data such as map data or historical and/or current trafficflow information may be used to supplement navigational data 324. Asanother example, third party services 306 may authenticate users onbehalf of the backend server 302 (e.g., through an account of the userwith the third party). Business logic 328 may comprise any suitablelogic operable to receive requests for data from backend system 116and/or mobile devices 104 and 108 and provide responses to the requests.

Backend server 302 may be in communication with each passenger mobiledevice 104 and each driver mobile device 108 that is utilizing the taxiservice at a particular time. Backend server may store informationreceived from the mobile devices 104 and 108 in data store 304. Backendserver 302 may also receive and respond to requests made by mobiledevices 104 and 108 by processing information retrieved from data store304.

When a passenger opens the taxi passenger application, the backendserver 302 may log the passenger in based on a comparison ofauthentication information provided by the passenger mobile device 104with authentication information stored in passenger account data 316.The passenger may then request a ride. The request is received by thebackend server 302 and stored in passenger request data 320. Backendserver 302 may access driver availability data 322 to determine one ormore drivers that would be suitable to fulfill the request from thepassenger. In one embodiment, backend server 302 selects a particulardriver (e.g., based on the driver's locality with respect to thepassenger's pick-up location) and sends information associated with therequest to the driver. The driver indicates whether he accepts orrejects the request via his mobile device 108. If the driver rejects therequest, backend server 302 selects a different driver and the processis repeated until the backend server 302 receives an accepted requestfrom a driver. In another embodiment, backend server 302 may select aplurality of drivers that may fulfill a passenger's request and allowthe passenger to select one of the drivers. The backend server 302 mayproceed to notify the driver of the request in a similar manner to thatdescribed above. In yet another embodiment, backend server 302 mayselect a plurality of drivers that may fulfill a passenger's request andnotify each driver of the passenger's request. The backend server 302may then allocate the request to one of the drivers based on anysuitable criteria. For example, the driver who is the first to acceptthe request may be assigned to the request. As another example, ifmultiple drivers accept the request within a given timeframe, therequest may be assigned to the most suitable driver (e.g., the driverthat is closest to the pick-up location or a driver that has a car thatmeets preferred characteristics of the passenger's request).

Once the request has been accepted by a driver, the backend server 302notifies the passenger that a driver has accepted his request andprovides any suitable information associated with the driver (e.g.,driver's current location, model and color of vehicle, estimated time ofarrival, etc.) to the passenger.

The backend server 302 may provide navigation information to the drivermobile device 108 to direct the driver to the passenger's pickuplocation and subsequently to direct the driver to the passenger'sdestination location. The backend server 302 may also provide real-timeupdates associated with the trip to both the passenger and the driver.

Once the passenger's destination location has been reached, the backendserver 302 may facilitate payment of the fare for the trip using paymentinformation stored in passenger account data 316 and/or driver accountdata 318 (or information supplied by the passenger at the time of thetransaction). The backend server 302 may also receive ratings associatedwith the trip for the passenger and driver and store these ratings indata store 304.

Backend server 302 may, in conjunction with data store 304, track andmanage the distribution of merchandise inventory held by drivers andpassengers associated with the taxi service. Any suitable merchandisemay be dispensed among drivers and passengers. Nonlimiting examples ofmerchandise include a mobile telephone, rechargeable batteries formobile telephones or other computing devices, portable power banks,battery chargers including power cables (e.g., with Universal SerialBus, Lightning, or other connectors), umbrellas, raincoats, and otherportable items.

Backend server 302 may communicate with mobile devices of drivers orother sources to track the inventory possessed by drivers and tofacilitate inventory restocking. For example, backend server 302 mayreceive notifications from a driver mobile device when the driver hasadded merchandise to the driver's inventory or dispensed merchandise toa passenger or other driver and may update data store 304 accordingly.Backend server 302 may also detect that particular merchandise has runout or is getting low and may notify the driver mobile device of such.In some embodiments, when backend server 302 detects depletion of aparticular item (or combination of items), it may provide the driverwith information on the location of the nearest distribution center oranother driver that has the needed merchandise. In a particularembodiment, backend server 302 may also track the usability of items inpossession of the driver and may factor the usability of the items intowhether the driver is in need of additional items. For example, if oneor more batteries in possession of the driver is in a low charge state,the backend server 302 may instruct the driver to obtain more batteriesor may notify the driver to charge the batteries. In some embodiments,backend server 302 may direct the driver to another driver or adistribution center from which the driver may pick up additionalinventory items to restock his supply. In various embodiments, driversmay drop off inventory items at the distribution center (e.g., batteriesneeding charging or items needing repair). In some embodiments, when adriver picks up merchandise from another driver, backend server 302 maycommunicate with both drivers to efficiently guide them to a meetingspot where the exchange can take place. In one embodiment, backendserver 302 may notify drivers when they are close to a distributioncenter (e.g., when they are located within a predetermined distance ordriving time from the distribution center).

Backend server 302 may facilitate the offering of inventory topassengers. For example, backend server 302 may prompt a driver throughthe taxi driver application to verbally offer one or more items ofmerchandise to a passenger. As another example, backend server 302 maycommunicate with a taxi passenger application to offer one or more itemsof merchandise to a passenger (e.g., via a GUI of the taxi passengerapplication).

In particular embodiments, the merchandise may be offered to a passengerprior to or concurrent with a ride request generated by the passenger.For example, when making a ride request, a passenger may indicate thathe would like a vehicle that is able to provide particular merchandise.In such embodiments, backend server 302 may select one or more vehiclesthat currently has the indicated merchandise and may alert thosevehicles of the ride request. Upon acceptance of the ride request by asuitable driver, the vehicle with the merchandise will be routed to thepassenger to fulfill the ride request. The backend server 302 may alsonotify the driver through the taxi driver application that themerchandise has been requested.

In particular embodiments, in response to an acceptance by a driver of aride request, a detection that a ride has begun, a detection that thedestination location of the ride request has been reached, or user inputinto the taxi passenger application, or other stimulus, the backendserver 302 may send the taxi passenger application informationassociated with the merchandise available in the vehicle fulfilling theride request. For example, a list of the items available may be sent,along with terms (e.g., price, borrowing periods, late fees, etc.) thatapply to the items.

In various embodiments, merchandise may be offered to a passenger (e.g.,via the taxi passenger application or by prompting driver through thedriver passenger application to offer the merchandise) in response to adetection that the merchandise is likely to be needed. For example, anumbrella may be offered in response to the backend server 302determining that it is currently raining or will rain in the near future(e.g., via a weather forecast or via sensors associated with thedriver's vehicle). As another example, a battery charger, battery pack,or battery may be offered to a passenger in response to a determinationthat a battery of a mobile device of the passenger is below apredetermined threshold (e.g., in one embodiment, the taxi passengerapplication may sense the battery level of the passenger's mobile deviceand initiate the offer or provide the sensed battery level to backendserver 302 which may then initiate the offer). As yet another example, amobile device or component thereof (e.g., a Subscriber Identity Modulecard) conforming to a particular locale (e.g., the locale of thedestination location of the ride) may be offered in response to adetermination that the passenger is from a different locale (e.g., froma different country) based on passenger account data 316 or otherinformation source.

In particular embodiments, the taxi service may be selective as to whenmerchandise is offered to a passenger. For example, in some embodiments,merchandise may only be offered to selected passengers, such as thosehaving a premium subscription to the taxi service, customers thatfrequently use the taxi service, or new customers on which the taxiservice is seeking to make a good impression. The suitability of apassenger may be based on a transaction history of the passengerincluding any suitable information associated with the passenger, suchas how long they have been registered with the taxi service (e.g.,preference might be given to relatively new and/or longstandingcustomers), how many rides they have requested through the taxi service,how often they request rides through the taxi service, an aggregatevalue of the rides the passenger has requested through the taxi service,an average value of rides the passenger has requested through the taxiservice, other suitable factors, or any combination thereof. In variousembodiments, the suitability of the passenger may be used to determinewhether to offer a particular passenger one or more items. Thesuitability of the passenger may also be used to set the terms of theoffer (e.g., price, the length of the borrowing period, late fees, latefee maximum, etc.) with passengers having higher suitability beingoffered better terms.

In various embodiments, the amount of inventory in the vehicleassociated with the driver may be used in conjunction with thesuitability of the passenger to determine whether to offer merchandiseto a particular passenger. For example, if the amount of merchandise inthe vehicle is relatively low, the taxi service may be relatively moreselective about which passengers are offered merchandise as compared toan instance where the amount of merchandise in the vehicle is larger.

After a determination that merchandise should be offered to thepassenger is made, the merchandise and the terms associated with theoffer are presented to the passenger (e.g., verbally by the driver,through a taxi passenger application, or via other means). The passengermay accept or reject the offer verbally (after which the driver mayenter acceptance of the offer through his taxi driver application), viataxi passenger application, or through other means. In variousembodiments, the decision may be communicated to backed server 302 whichmay then update data store 304 if necessary. For example, if thepassenger accepts the offer, the backend server 302 may cause an entryfor the passenger to be created or updated in passenger inventory data332. In addition, the backend server 302 may cause an entry associatedwith the driver in the driver inventory data 334 to be updated toreflect the dispensed merchandise.

If the merchandise was borrowed by the passenger, the passenger mayreturn the merchandise to another driver associated with the taxiservice (e.g., in conjunction with a passenger requesting an additionalride from the taxi service) or to another location associated with thetaxi service (e.g., a distribution center). The returned merchandise maybe scanned in or otherwise entered via a taxi driver application orother logic and reported to backend server 302 which may update theappropriate entries in passenger inventory data 332, driver inventorydata 334, and/or general inventory data 336.

In various embodiments, if the item has been returned late, processingof the late fee may be initiated in response to the item being returned.In other embodiments, processing of a late fee may occur at any suitabletime, such as periodically (e.g., daily) after an item is due or after aparticular amount of time has passed since the due date. In someembodiments, after a passenger borrows an item, they may decide to keepthe item and may either pay the maximum late fee penalty or indicate thepurchasing of the item via their taxi passenger application. In variousembodiments, the backend server 302 may send reminders to the passengermobile device 104 or other device associated with the passenger (e.g.,via a text message or through passenger application logic 218)indicating when the item is due, late fees that will be applicable ifthe item is not returned on time, where the item may be returned to, orother information associated with the item.

FIG. 4 illustrates example passenger inventory data 332 in accordancewith certain embodiments. In the embodiment depicted, passengerinventory data 332 includes an entry 400 for each of four distinctpassengers, though passenger inventory data 332 may include any suitablenumber of entries for each passenger of any suitable number ofpassengers. Each entry 400 includes a field 402 for identifying apassenger, a field 404 for identifying one or more items that arecurrently in possession by the passenger, a field 406 for identifyingwhen each item was borrowed by the passenger, a field 408 foridentifying when each borrowed item is due, a field 410 for identifyingthe late fee associated with the borrowed item, and a field 412 foridentifying the maximum late fee that is to be charged for the borroweditem. As in the depicted embodiment, the terms for borrowing an item mayvary based on the passenger and/or item borrowed. For example, in theembodiment depicted, passenger 4 is provided with better terms (longerborrowing period and a lower late fee rate) for borrowing an umbrellawhen compared to passenger 1. As described above, the difference interms may be based on any suitable factors, such as the suitability ofthe particular passengers.

FIG. 5 illustrates example driver inventory data 334 in accordance withcertain embodiments. In the embodiment depicted, driver inventory data334 includes an entry 500 for each of four distinct drivers, thoughdriver inventory data 334 may include any suitable number of entries foreach driver of any suitable number of drivers. Each entry 500 includes afield 502 for identifying a driver and fields 504-510 for identifyingthe quantity of items currently in possession by the correspondingdriver.

FIG. 6 illustrates a method for distributing an inventory item to apassenger of a taxi service in accordance with certain embodiments. Thesteps of the method may be performed by any suitable entities (e.g.,passenger mobile device 104, driver mobile device 108, or backend server302) described herein alone or in combination with one or more otherentities. At step 602, a transportation request is received from apassenger. At step 604, a driver is directed to fulfill thetransportation request. At step 606, it is determined whether amerchandise item should be offered to the passenger. This determinationmay be made at any suitable time, such as prior to, during, or after theride is complete. The determination may be made based on any suitablefactors, such as whether the passenger has requested merchandise,whether a need for the merchandise is detected, the amount ofmerchandise in the vehicle, the suitability of the passenger, otherfactors, or any combination thereof.

If it is determined that an offer should not be made, the method ends.If it is determined that an offer should be made, then the merchandiseand related terms are offered to the passenger at step 608. Inparticular embodiments, the terms of the offer may be based on anysuitable factors such as those listed above with respect to the factorsused to determine whether the offer is made. In addition, late fees,late fee maximums, or purchase prices may be based on set values foreach type of merchandise such as the cost of an item. In variousembodiments, these set values may then be adjusted based on any of thefactors mentioned above.

At step 610 it is determined whether the merchandise offer has beenaccepted. If the merchandise offer is not accepted, the method ends. Ifthe merchandise offer is accepted, a data store is updated at 612. Forexample, the terms of the offer and an indication that the passenger hasaccepted the offer may be recorded in a data store. As another example,the inventory held by the driver may be updated to reflect the transferof one or more merchandise items from the driver to the passenger.

Some of the steps illustrated in FIG. 6 may be repeated, combined,modified or deleted where appropriate, and additional steps may also beincluded. Additionally, steps may be performed in any suitable order orconcurrently without departing from the scope of particular embodiments.

It is also important to note that the steps in FIG. 6 illustrate onlysome of the possible scenarios that may be executed by, or within, thevarious components of the system described herein. Some of these stepsmay be deleted or removed where appropriate, or these steps may bemodified or changed considerably without departing from the scope of thepresent disclosure. In addition, a number of these operations may havebeen described as being executed concurrently with, or in parallel to,one or more additional operations. However, the timing of theseoperations may be altered considerably. The preceding operational flowshave been offered for purposes of example and discussion.

The functionality described herein may also be performed by any suitablecomponent of the system. For example, certain functionality describedherein as being performed by backend server 116, may, in variousembodiments, be performed by any combination of one or more passengermobile devices 104 or driver mobile devices 108 where appropriate.Similarly, certain functionality described herein as being performed bya passenger mobile device 104 or a driver mobile device 108 may, invarious embodiments, be performed by backend server 116 whereappropriate.

Numerous other changes, substitutions, variations, alterations, andmodifications may be ascertained to one skilled in the art and it isintended that the present disclosure encompass all such changes,substitutions, variations, alterations, and modifications as fallingwithin the scope of the appended claims. In order to assist the UnitedStates Patent and Trademark Office (USPTO) and, additionally, anyreaders of any patent issued on this application in interpreting theclaims appended hereto, Applicant wishes to note that the Applicant: (a)does not intend any of the appended claims to invoke paragraph six (6)of 35 U.S.C. section 112 as it exists on the date of the filing hereofunless the words “means for” or “step for” are specifically used in theparticular claims; and (b) does not intend, by any statement in thespecification, to limit this disclosure in any way that is not otherwisereflected in the appended claims.

What is claimed is:
 1. A method comprising: receiving a transportationrequest from a passenger having an account with a taxi service;directing a driver associated with the taxi service to pick up thepassenger and transport the passenger to a location specified by thepassenger; determining that the passenger should be offered an item ofmerchandise to use temporarily; and in response to the passengeraccepting the item of merchandise, sending an update to a data store,the update indicating that the passenger is in possession of the item ofmerchandise.
 2. The method of claim 1, wherein the determination thatthe passenger should be offered an inventory item is based at least on anumber of items of merchandise located in a vehicle associated with thedriver.
 3. The method of claim 1, wherein the determination that thepassenger should be offered an item of merchandise is based at least ona transaction history of the passenger with the taxi service.
 4. Themethod of claim 1, further comprising determining a length of time thatthe passenger may keep the item of merchandise without being charged forthe item.
 5. The method of claim 1, wherein the data store tracks thenumber of items of merchandise located in a plurality of vehiclesassociated with the taxi service.
 6. The method of claim 1, wherein theitem of merchandise comprises an umbrella, a mobile device battery, amobile device charger, a mobile device, or a Subscriber Identity Module(SIM) card.
 7. The method of claim 1, further comprising determiningthat a second passenger should not be offered an item of merchandise touse temporarily based at least in part on a transaction history of thesecond passenger with the taxi service.
 8. The method of claim 1,further comprising in response to the passenger returning the item ofmerchandise to a different driver associated with the taxi service,sending a second update to the data store, the second update indicatingthat the passenger has returned the item of merchandise.
 9. The methodof claim 1, further comprising updating, in the data store, an inventoryof merchandise items located in a vehicle associated with the driver toreflect the item of merchandise being accepted by the passenger.
 10. Themethod of claim 1, wherein the transportation request received from thepassenger comprises a request for the item of merchandise.
 11. A systemcomprising: a communication interface; a data store; and at least oneprocessor to: receive a transportation request from a passenger havingan account with a taxi service; direct a driver associated with the taxiservice to pick up the passenger and transport the passenger to alocation specified by the passenger; determine that the passenger shouldbe offered an item of merchandise to use temporarily; and in response tothe passenger accepting the item of merchandise, send an update to thedata store, the update indicating that the passenger is in possession ofthe item of merchandise.
 12. The system of claim 11, wherein thedetermination that the passenger should be offered an inventory item isbased at least on a number of items of merchandise located in a vehicleassociated with the driver.
 13. The system of claim 11, wherein thedetermination that the passenger should be offered an item ofmerchandise is based at least on a transaction history of the passengerwith the taxi service.
 14. The system of claim 11, wherein the at leastone processor is further to notify the driver when merchandise of thedriver falls below a threshold level, wherein notifying the driverincludes sending the driver directions for replenishing the merchandise.15. The system of claim 11, wherein the at least one processor isfurther to in response to the passenger returning the item ofmerchandise to a different driver associated with the taxi service, senda second update to the data store, the second update indicating that thepassenger has returned the item of merchandise.
 16. At least onecomputer-readable non-transitory media comprising one or moreinstructions that when executed by at least one processor configure theat least one processor to cause the performance of operationscomprising: receiving a transportation request from a passenger havingan account with a taxi service; directing a driver associated with thetaxi service to pick up the passenger and transport the passenger to alocation specified by the passenger; determining that the passengershould be offered an item of merchandise to use temporarily; and inresponse to the passenger accepting the item of merchandise, sending anupdate to the data store, the update indicating that the passenger is inpossession of the item of merchandise.
 17. The at least one media ofclaim 16, wherein the determination that the passenger should be offeredan inventory item is based at least on a number of items of merchandiselocated in a vehicle associated with the driver.
 18. The at least onemedia of claim 16, wherein the determination that the passenger shouldbe offered an item of merchandise is based at least on a transactionhistory of the passenger with the taxi service.
 19. The at least onemedia of claim 16, wherein the operations further comprise determining alength of time that the passenger may keep the item of merchandisewithout being charged for the item and charging the passenger a late feewhen the passenger fails to return the item of merchandise within thelength of time.
 20. The at least one media of claim 16, wherein theoperations further comprise in response to the passenger returning theitem of merchandise to a different driver associated with the taxiservice, sending a second update to the data store, the second updateindicating that the passenger has returned the item of merchandise.